fix: honor recovered E2E retries - #2400
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe CI workflow now prevents E2E report publication errors from failing the workflow. A shell test extracts the live report step and verifies ChangesE2E report publishing
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to The CI workflow now preserves successful E2E results when retries recover an initially failing test, with a matching contract test; no actionable merge-blocking risk remains. Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🚀 PR Preview Install Guide🧰 CLI updatenpm i -g https://pkg.pr.new/larksuite/cli/@larksuite/cli@c7438c7e74e05dc97c0aff8c56889a59890ea9a0🧩 Skill updatenpx skills add Tantanz20020918/cli#fix/e2e-retry-report-status -y -g |
cd48dfc to
c7438c7
Compare
Summary
Prevent the JUnit publishing step from marking live E2E as failed when gotestsum successfully recovers an initially failing test through its configured retries.
Changes
Test Plan
make script-test(164 tests passed).Related Issues